home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
029a
/
scc.zip
/
SAMPLE.V2
< prev
next >
Wrap
Text File
|
1991-09-11
|
13KB
|
326 lines
*** Please Read the following information ***
The SCC generated sample.log file should be viewed from within the
SCC VIEW utility. Therefor to build the sample.log file, start by
typing at the DOS prompt "sample". This "sample.bat" (batch) file will
automaticaly build the log file. The "sample.bat" (batch) file will
also bring up the SCC VIEW utility. Then continue reading the following.
Invest only 15 minutes of your time, and discover the "Advantage" of
SCC's small CASE utility and its ease of use. This example log file
will review a typical SCC generated change LOG.
Some of the "LOG" build options set (see above log header) for this
SCC example VIEW utility are set as:
Group Match = 6
Log Detail = Yes fixed default for Sharware
Strip End White = No strip ending white space from Old/New
Ignore Case = Yes
Ignore White = Yes
Ignore Numbers = Yes
If you have a color monitor (for the enhanced view), please note:
1) Main "text" screen attributes (foreground/background):
o CONTROL = High White & Blue Background.
o Old Document = Light White & Blue Background.
o New Document = Yellow & Blue Background.
2) Cursor line attributes:
o Cursor = Black & Cyan Background.
Note... The log status within the cursor position will show
special symbol that reflect the SCC Log control operations, such
characters as '-', '+', '.' or blank ' '.
When the cursor is on a Log line (the left control side) that
has either '-', or '+', then one of the following line operations
will apply.
Log status Operation
---------- ---------
'-' " Deleted Line
'+' " Inserted Line
When the cursor is on a Log line (the left control side) that
equals a blank character ' 'one of the following line operations
apply. This greatly simplifies the reading of the printed Log,
thus helping to eliminate (unimportant) selected changes.
Log status Operation
---------- ---------
' ' " Moved Line "
' ' " Ignore White Sp "
' ' " Ignore Numbers "
' ' " Ignore Case "
' ' " Multi Opt Match "
When the cursor is on a Log line (the left control side) that
has a period '.', then that line is common to both the files Old
and New.
Log status Operation
---------- ---------
'.' " Common Lines "
The above SCC Log (along with different SCC Log option settings)
can help generate a "filtered" SCC change control report Log to
what is important (delete or insert status) and not important
(blank status) in your file.
For example you may not want the '-' or '+' (delete or insert)
Log status characters for such lines containing differences of
only "White Space", "Upper/Lower Case" etc.
At any time you may press the
F1 key for the help menu.
F2 key for the QUICK help menu.
START OF EXAMPLES.....
" Common Lines "
Common Line numbers between the Old and New documents. Cursor
status will show the corresponding Old line #.
" Inserted Lines "
Will show what line and line # that was inserted into the New.
" Ignore White Sp "
All the text match except for white space between documents.
" Ignore 1234 Numbers "
4321 All the text match except for numbers 5678between documents.
" Ignore Case "
All the text match except for upper/lower case between documents.
" Multi 456 Match "
All the TEXT match by using two 3 or more options between the OLD
and NEW documents. For example if the option "Ignore Case" and
"Ignore numbers" allowed the 456 lines match then this status.
" Moved Lines "
These are exact matching lines between documents but may have
different line numbers.
Strip End White
If "Strip End White" was selected the following lines will be
exactly alike (same length) and would show as "Common Lines".
If "Strip End White" was ** NOT ** selected then the lines
will be of different lengths.
Common lines
These lines are common between the Old and New documents.
** Note ** SCC can also track and VIEW any (ASCII TEXT)
formatted document such as the following.
Page 1 Overview.scc
Software Change Control (SCC)
Softime Systems
P.O. Box 2447
Lake Ronkonkoma LI. NY 11779
(516) 981-8386
Copyright (c) 1990-91 by Walter Erickson
All Rights Reserved.
"A small CASE for a big problem"
Mary J Erickson
Page 2
Overview
Common questions about SCC
What is SCC ?
-------------
Software Change Control (SCC), as the name implies, is one of the most
powerful and cost-effective tool available in this emerging field of CASE.
SCC features friendly menu-driven interfaces (with automatic context help)
suitable for use by non-technical administrative, as well as for the
sophisticated user.
SCC closely tracks (logs) all software/text changes between two similar
source files, thereby giving a complete (version to version) audit trail.
A SCC generated Log greatly simplifies any user request for the
(identification) of what, when and why changes were made.
What does SCC do ?
------------------
When SCC is run the tracking (output) log file will then reflect (in
context) what changes have occurred between the two (input) source files,
thus allowing the programmer and/or management to have a clear visual SCC
log of all software and/or text changes.
This feature enables the user to control all enhancements and
documentation of source data at this critical level.
Why is SCC needed ?
-------------------
All software source files will need changes. In fact, it is a truism that
every software project released, including those released quite recently,
need changes. The most important consideration at this stage is to regulate
and control the documentation and its changes.
SCC is a decomposition process that offers a complete and precise
description of what (line-by-line) changes have occurred between two source
files. This results in faster development time, along with software that is
far less likely to fail in use.
Page 3
Can managers use SCC ?
----------------------
The management of software changes at the programming (source) level
(generally accepted as the most expensive and weakest link in software
management) is one of the most difficult problems managers and programmers
alike have.
Using SCC creates an environment that is very time and cost effective.
SCC allows changes to be made in a more maintainable, reliable and
controllable way; that is, software control is fully documented, along with
a full audit trail of what changes have occurred between software versions.
SCC greatly improves the suitability and appropriateness of software
change documents; enhances clarity, readability, reliability and complete
recoverability; allowing software changes to be a great deal easier to
track and maintain.
Does SCC require a special editor ?
-----------------------------------
No, all that is required is that the input source files to SCC be in
(ASCII TEXT) format.
Does SCC require a data base ?
------------------------------
No, SCC can either be integrated into a data base or stand alone, for
most small projects a data base is not necessary, thus eliminating
complexity and cost (KISS). All header file-id, code and documentation
changes "between versions" are kept within the SCC Log itself.
Can I run SCC against existing versions ?
-----------------------------------------
Yes, you can build new and complete SCC change logs from older existing
(version to version) files, this will give a entire audit trail of any
software changes between versions.
What can SCC be used for ?
--------------------------
o Documenting
o Software/text control
o Software Debugging
o version pre-release (development) change control
o Code walkthrough's
o etc.
Using SCC for Documenting
-------------------------
When SCC is run, the tracking (output) log file will then reflect (in
context) what changes that have occurred between the two (input) source
files, thus allowing the programmer and/or management to control, enhance
and document software at this critical source level.
SCC generates a software change (log) that closely tracks and records all
changes consisting of a header, control change numbers and special symbols
to reflect the operations of delete '-', insert '+', move ' ' etc.
Page 4
Using SCC for Software control
------------------------------
The manager/programmer can visually see on one listing (the change log)
all changes and special tracking symbols that were necessary to build the
later version from the earlier version, thus keeping an accurate control
over all changes.
SCC will also reveal all unintentional and possible unauthorized changes
to source files, thus preventing future problems in the next released
version.
SCC helps the programmer and manager to make changes, "edit out" any
tactical coding/design errors between two source files. This can be done by
using a similar method such as the following:
Initial Technical Design Review
o revision of raw draft coding design
o clarification of ambiguous design content
o identification of coding gaps and inconsistencies
o discovery of major/minor coding errors
Quick Coding Review
o verification of technical content NOT already tested or
debugged
o incorporation of late technical coding changes
o writing specs for changed documentation
Final Technical Design Review
o refining the source code/documentation for usability
o minor "edit" cleanup
o careful configuration control and test proofing
Field Maintenance of Released Software
o discovery of unintentional coding errors
o discovery of undocumented features
o uncovering code that once worked, but now does not
o SCC Log header information for release identification and control
Page 5
SCC summary
-----------
SCC is a comprehensive utility designed to compare two files and generate
various reports (log files) that display any or all change differences as
they evolve.
SCC log records who, why, when and where changes were made, thus
maintaining a complete history of all changes.
SCC enables detailed verification of auditing accuracy, eliminates
undetected programming errors and drastically reduces manual desk checking
time.
The manager/programmer knows exactly what the changes are between
versions.
SCC accepts (ASCII TEXT) output from your favored editor.
You can build new and complete SCC change logs from older existing
(version to version) files.
You can track any coding progress on software changes by viewing an SCC
log against the previous and/or developing files.
You can backtrack to any previous version to examine what changes created
that release at that time.
SCC change log report (version to version) can greatly help in debugging
changes between versions (one works the other does not).
You can build new and complete SCC change logs from older existing
(version to version) files.
The key benefits of SCC are:
o lower project costs
o controlled release management
o structured walkthroughs
o faster software coding thruput
o higher software quality
If you would like further information about this or the SCC registered
programs, please call Walter Erickson at (516) 981-8386